Instead of writing errors to
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Sun, 23 Oct 2005 21:34:13 +0000 (22:34 +0100)
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Sun, 23 Oct 2005 21:34:13 +0000 (22:34 +0100)
commit4384b3fc7028be8e027d984e4f7e38a0d488211d
treea4242b66e867895624e3d1058179c78603c43065
parentdab3d2969db5dca7011c185af76b188b21e08e44
Instead of writing errors to
/local/domain/0/backend/<devclass>/<dom>/<devid>/error, write them instead to
/local/domain/0/error/backend/<yada>.  This is not the best place for them
perhaps, but it moves them out of the backend directory, on which the drivers
have a watch.  This fixes the problem whereby writing an error will trigger a
watch, causing the error message to be written again, and repeat.  Fixes bug
#286.

Signed-off-by: Ewan Mellor <ewan@xensource.com>
linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c
tools/examples/xen-backend.agent
tools/python/xen/util/diagnose.py